Method and Apparatus for Finding and Accessing a vehicle Fueling Station, Including an Electric Vehicle Charging Station

ABSTRACT

A control system and method are provided for a station to dispense fuel to a vehicle, including an electric vehicle, without requiring dedicated access to a communications network, with the advantage that authorization for fleet vehicles or individuals can be obtained from an access management system, using a portable, wireless device, such as a smart phone or a dashboard appliance. The authorization is wirelessly relayed to the station by the wireless device, to enable the dispensing of fuel. Subsequently, a log comprising the transaction is provided to the access management system, through the same or a different wireless, mobile computing device. The log may also report status and other events, such as load shedding.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 13/429,439, filed Mar. 26, 2012, which is acontinuation-in-part of International Patent Application No.PCT/US11/26781, filed Mar. 2, 2011, which claims benefit to U.S.Provisional Patent Application Ser. No. 61/309,813, filed Mar. 2, 2010,each of which is incorporated herein by reference in their respectiveentireties.

FIELD OF THE INVENTION

The present invention relates generally to a system and method forcontrolling access to a vehicle fueling station. More specifically, thepresent invention relates to a system and method for finding andaccessing a vehicle refueling station, of which an electric vehiclecharging station is an example.

BACKGROUND OF THE INVENTION

A drawback that inhibits wide adoption of electric vehicles is the lackof infrastructure for conveniently charging them; and while hybridelectric vehicles are increasingly popular, plug-in versions thatoperate to maximize use of their battery and minimize use of theirgasoline-fueled generator are rare, in part due to the same lack ofpervasive infrastructure.

Provision of a vehicle charging infrastructure is inhibited bycomplexity: Such infrastructure is expensive, typically requiring notonly provision of power, but also of communication services that (if andwhen available) represent an ongoing operational expense. In some cases,wired communication channels can be used to allow a charging station tocommunicate with external systems, for example, a merchant bank forclearing credit and debit card transactions. However, that suggests apervasive communications infrastructure for every charging station.While wireless technologies can be employed for such communicationchannels in some circumstances, in some cases they are difficult toconfigure and make reliable, for example, in subterranean parkingstructures and some city streets where the positions of vans and trucksmight screen a transceiver from a communication signal. Such wirelesscommunications may be expensive. Other efforts to provide communicationthrough the power grid require extensive, pervasive, and expensivechanges to the grid itself, in order to make such communicationavailable wherever needed.

While the need to address these issues with respect to electric vehiclecharging has generated the following solution, the solution itself ismore generally applicable, for example to other forms of vehiclefueling.

OBJECTS AND SUMMARY OF THE INVENTION

The present invention relates generally to a system and method forrefueling vehicles. More specifically, the present invention relates toa system and method for finding and accessing a fueling station forvehicles, including an electric vehicle charging station. That is, thepresent invention makes identifying an appropriate fueling stationeasier and more efficient, can provide a parking and reservation system(most pertinent to EV charging stations), and mediate access between avehicle's on-board communications system or user's smart phone and afueling station.

Presently, facility owners wishing to provide electrical vehiclecharging stations need to identify a location to be reserved for vehiclerecharging, provide electric service to that location, and installElectric Vehicle Service Equipment (EVSE, that is, a charger or chargingstation). If they choose to require payment for the electricity used tocharge the vehicle, typical installations require communication also beprovided. In the case of equipment located near communications closetsin parking structures this is easier, as it is if the parking is in theopen air or other area well served by long range wireless technology,such as cell phone coverage or Wi-Fi. But wireless connections can betenuous, potentially being attenuated by a parked truck or completelyabsent in an underground parking facility.

There is a further need to provide such fueling infrastructure in amanner that can minimize labor and materials costs, maintainsreliability, and is arbitrarily scalable.

Further still, there is a need to permit such installations to operateon an individual basis, without a requirement that an entireinfrastructure have first been converted to a new standard. This isparticularly true for communication-over-power line systems that requirenot only bridging of communications over power lines at chargingequipment, but also at every breaker panel and transformer between thecharging station and the gateway to pre-existing communicationschannels. Failing implementation of a comprehensive data-over-power lineinfrastructure, support for such communication will be spotty,potentially for decades.

Further, there is a need for such fueling infrastructure to facilitatefinding a location with a minimum of difficulty and delay, and ideally,in a way that maximizes convenience and confidence, for example, bysupporting reservations for parking and charging, which can beespecially valuable for electric vehicle recharging.

The present invention satisfies these and other needs and providesfurther related advantages.

Herein, the term “charging station” includes Electric Vehicle SupplyEquipment (EVSE), as the charging stations for modern electric vehiclesare formally known in standards such as the Society of AutomobileEngineers (SAE) standard J1772:2010 for their Electric Vehicle andPlug-in Hybrid Electric Vehicle Conductive Charge Coupler. Further,while the discussion herein is presented in the context of an electricvehicle and uses charging stations as the primary example, the teachingsherein for an access management system apply to a more general“dispensing station” for vehicles, a term used herein to encompass notonly charging stations, but also other fueling stations, such as forgasoline or compressed natural gas (CNG).

The term “access management system”, as used herein, includes “parkingmanagement system”, as might be used by parking lot owners to administeraccess to the parking spaces, lots, or areas they manage and thecharging stations located therein. The term also applies to “fleetmanagement systems”, which administer access to fueling stations for thevehicles of their fleets. The term also applies to “fueling stationmanagement systems”, for example as might be owned by an oil company, tocontrol access for individuals to fueling stations operated or managedby the company. Herein, the main example embodiment is of electricvehicle charging stations managed by a parking management system, andthese terms will be encountered most often, but the invention isapplicable to any of these access management systems.

It is an object of the present invention to provide a way for amanagement system to monitor the status of, and control access to, afuel dispensing station for vehicles, which may be a charging stationfor electric vehicles, where the management system can remote from, andmay have no real-time communication with, the dispensing station.

It is an object of the present invention to provide control through awireless, mobile computing device, such as a smart phone, or anin-vehicle dashboard appliance.

It is an object of the present invention for a wireless, mobilecomputing device to carry authorizations from the management system tothe dispensing station.

It is an object of the present invention for a wireless, mobilecomputing device to carry transaction records from the dispensingstation to the management system.

It is an object of the present invention for a wireless, mobilecomputing device to carry status records from the dispensing station tothe management system.

It is an object of the present invention for a wireless, mobilecomputing device to carry receipt acknowledgments for log records fromthe management system to the dispensing station.

It is an object of the present invention for a wireless, mobilecomputing device to carry software upgrades or policy updates from themanagement system to the dispensing station.

It is an object of the present invention for a first dispensing stationto exploit a communication connection with a second dispensing stationto facilitate communication between the first dispensing station and themanagement system.

It is an object of the present invention to provide a softwareapplication for a smart phone or a dashboard appliance to facilitatecommunication between a management system and a dispensing station.

It is an object of the present invention to facilitate the finding of anavailable and ready dispensing station, including the finding of aparticular dispensing station.

It is an object of the present invention to allow any of thecommunications between the management system and the dispensing stationto be secure and/or authenticable.

It is an object of the present invention to permit the assignment of aparticular dispensing station in response to a request for access to adispensing station.

It is a primary object of the present invention to minimize costs ofinstalling a fueling infrastructure, such as for electrical vehiclecharging, while providing a convenient, robust, and secure userexperience for operators and patrons of the system.

BRIEF DESCRIPTION OF THE DRAWINGS

The aspects of the present invention will be apparent upon considerationof the following detailed description taken in conjunction with theaccompanying drawings, in which like referenced characters refer to likeparts throughout, and in which:

FIG. 1 illustrates an electric vehicle approaching multiple chargingstations;

FIG. 2 illustrates an interaction between a patron and/or vehicle with acharging station;

FIG. 3 is a diagram showing a transaction sequence between a wirelessdevice (e.g., a smart phone), an authorizing server, and multiplecharging stations;

FIG. 4 is a diagram showing another embodiment of the transactionsequence;

FIG. 5 is a diagram showing still another embodiment of the transactionsequence;

FIG. 6 is flowchart showing a process implemented by the exampletransaction sequences of FIGS. 3-5;

FIGS. 7A and 7B are example parking certificate files;

FIG. 8 is an example log data file compiled by a charging station to betransferred to a smart phone or otherwise communicated;

FIG. 9 is an example schema for a database suitable for tracking use ofthe charging stations as reported in log files;

FIGS. 10A and 10B are example acknowledgment files to be communicated toa charging station; and,

FIG. 11 is an example block diagram for a charging station of thepresent invention.

While the invention will be described and disclosed in connection withcertain preferred embodiments and procedures, it is not intended tolimit the invention to those specific embodiments. Rather it is intendedto cover all such alternative embodiments and modifications as fallwithin the spirit and scope of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Referring to FIG. 1, in approach situation 100, plug-in electric vehicle130, which may be a plug-in hybrid electric vehicle, approaches parkingspaces 110, 120, served by chargers 111, 121, respectively. Each charger111, 121, is equipped with a charge cable 112, 122, terminated with astandard connector, for example, one manufactured in accordance with theSociety of Automotive Engineers standard SAE J1772:2010.

In the present invention, as patron 131 approaches parking spaces 110,120 in vehicle 130, a wireless, mobile computing device 132 communicateswith chargers 111, 121. Wireless, mobile computing device 132 may be asmart phone, carried by patron 130, or a “dashboard appliance” carriedby vehicle 130, such as a removable GPS navigation device or onboardelectronics module integrated into the vehicle, configured, for exampleby application 133, to carry out the communications and transactionsdescribed herein. In many of the embodiments discussed, wireless device132 is described as a “smart phone” running application 133 forillustrative reasons, but it should be understood that these otherembodiments might be used instead in many of the example embodiments.

Each charger 111, 121 has an antenna 113, 123 and one or morecommunication modules (shown in FIG. 11) with which to carry out aninteraction with smart phone 132. Generally, wireless communicationcould be provided as optical, radio, infrared, or acousticcommunication. However, for this application, radio communication ispractical, and use of the internationally approved Industrial,Scientific, and Medical (ISM) bands is well suited, in particular the2.4 GHz band, which is used by the example radio communicationsstandards identified herein.

Smart phone 132 forms a wireless connection 142 with charger 121, in oneexample embodiment using Bluetooth®, (as described by Bluetooth SIG,Inc. of Kirkland, Wash. and published by them as the “BluetoothSpecification Version 4.0”, Jun. 30, 2010 and previous versions). Whenthis happens, the transaction results in charger 121 indicating thatparking space 120 is not available for vehicle 130. Example details forsuch a transaction are discussed below in conjunction with FIGS. 3-6.This indication may be made by a visible or audible signal made withsmart phone 132, or it may be indicated by charger 121, for example bylighting or flashing red light 124 (while green light 125 is unlit).

Smart phone 132 forms wireless connection 141 with charger 111, again byexample, using Bluetooth® or other wireless communication mechanism andprotocol. When this happens, the transaction results in charger 111indicating that parking space 110 is available either generally orspecifically for vehicle 130. Again, example details are discussed belowin conjunction with FIGS. 3-6. This indication may be made by a visibleor audible signal made with smart phone 132, or by charging station 111lighting or flashing green light 115 (while red light 114 remainsunlit).

In this way, patron 131 is directed toward parking spaces available foruse by vehicle 130. Absent the presence of smart phone 132 and wirelessconnections 141, 142, charger 121 would indicate “No Parking” with redlight 124, and, if parking space 110 is generally available, charger 111may continue to indicate “Parking Available” with green light 115, butif parking space 110 is specifically reserved for patron 131 or vehicle130 (or wireless device 132), then red light 114 would be lit toindicate “No Parking” until vehicle 131 approaches and the abovetransaction is conducted over wireless connection 141.

Turning to FIG. 2, parked situation 200 is shown, where electric vehicle130 has parked in parking space 110 and has been connected for chargingfrom charging station 111 through charging cable 112. Note that in someembodiments, the connection for charging may be inductive (not shown).In some embodiments, while in parking situation 200, charger 111 may beenabled by interaction with smart phone 132 through antenna 113 andwireless connection 201. Wireless connection 201 may be the same asconnection 141, e.g., Bluetooth®, or may be a different wirelessconnection, e.g., near field communication (NFC), or may include both.One example using NFC is discussed in conjunction with FIG. 4. Inanother embodiment, smart phone 132 may use a camera or other sensor(not shown) to read a barcode or other indicia (not shown) on orproximal to charging station 111 instead of an alternative wirelessconnection differing from connection 141. Such an embodiment is furtherdiscussed in conjunction with FIG. 5.

After an interval of time parking in space 110, as patron 131 returns,smart phone 132 may again form wireless connection 201 with chargingstation 111 to complete the charging transaction, and/or downloadinformation about the charging session. This may occur before or afterelectric vehicle 130 is disconnected from charge cable 112, and ifbefore, may disable the charging station. Example information that mightbe downloaded to smart phone 132 may be an electronic receipt detailingthe amount of energy drawn in the charging session, a billing amount, orother information such as whether the charging station 111 was a targetof a load shed event during the charging session, or whether maintenanceis required.

FIG. 3 shows a detailed transaction diagram for an assigned parkingtransaction sequence 300 occurring between smart phone 132 and a parkingmanagement system, represented by parking management server 305, andcharging stations 111 (also called ‘A’), and 121.

The vertical lines 301, 302, 303, and 304 correspond to smart phone 132,charger station 111, charger station 121, and parking management server305, with the many arrows among them (e.g. 311) representing messagessent by the entity from which the arrow points away and being sent tothe entity toward which the arrow points. So, the initial transaction311, in pre-registration phase 310 of assigned parking transactionsequence 300 is a request for parking from smart phone 132 to server305. Such a request might be made with an application 133 on smart phone132 able to contact server 305 via the cell phone network (not shown) torequest parking and charging immediately, or for a reservation at somespecified time and date in the future. The request may include anaccount ID or payment information (depending on the business policybeing implemented), and may include secure credentials (e.g., password)for authorization. The request may include a specification of where theparking is to be (e.g., in what parking facility), or may merelyindicate the general location (in which case, other patron-specifiedoptimizations such as minimizing cost or walking distance, may beprovided). In another embodiment, the connection to parking managementserver 305 may be through a connection at a parking access gate (notshown), such that request 311 occurs as the vehicle 130 is at theentrance to the parking lot comprising spaces 110, 120. In such anembodiment, the request for a parking space with a charging station iseffectively for immediate occupancy. Note that transaction 311 mustoccur from a location where smart phone 132 can obtain a connection toserver 305. As such, in some embodiments, parking request 311 and theresponses may be exchanged through a wired connection (e.g., while athome, through the Internet), rather than using a wireless connection.

In response to parking request 311, parking management server 305replies with a certificate B (in message 312) for specific charger A (inthis example, charging station 111). Server 305 may further reply withlog acknowledgment C (in message 313), a data file, also specificallyfor charger A. The use of the log acknowledgment C is discussed below inconjunction with FIGS. 10A, 10B and elsewhere, but its purpose is to letparking station 111 know what fraction of the logs kept by parkingstation 111 have been successfully transferred to parking managementserver 305, and can therefore be deleted. Both certificate B (in 312)and log acknowledgment C (in 313) should be digitally signed forsecurity using a signing certificate (not shown) trusted by charger A.Example embodiments of these two messages are discussed below inconjunction with FIGS. 7A and 10A.

During search phase 320, smart phone 132 may make unsuccessful attemptsto find charger A (111), for example with unacknowledged “looking for A”messages 321.

In an example embodiment using Bluetooth® as the wireless communicationchannel for connections such as 141, 142, then certificate B for chargerA may comprise the Bluetooth Device Address (BD_ADDR) for charger A.Thus, in a Bluetooth® embodiment, the search for charger A may compriseeither repeated page messages directed for the device address (BD_ADDR)corresponding to charger A.

If using page messages directed at charger A, then message 322, evenwhen actually received by another charger (e.g., 121), the other chargerwill not respond.

When “looking for A” message 323 is actually received by charger A(111), an acknowledgment message 324 from charger A will be returned tosmart phone 132: Charger A has been located. In one example embodiment,when “looking for A” message 323 is acknowledged, charger A (111) maystart flashing a green indicator 115.

In an alternative embodiment, “looking for A” messages 321, 322, 323,might be Bluetooth® inquiry messages, which chargers 111, 121 might bothacknowledge with their respective devices addresses (BD_ADDR).Application 133 would then look for the device address of charger A inthe inquiry responses received. The other charger's response (not shownin FIG. 3) will not include charger A's device address, and so may beignored.

During login phase 330, certificate message 331 is sent by smart phone132 to charger A thereby providing certificate B to charger A.Certificate B conveys to charger A the presenter's rights (e.g.,charging for a particular interval). Certificate B can be securelytrusted by charger A when the certificate is digitally signed by server305 using a signing certificate that charger A trusts.

If charger A (111) accepts certificate B, for example because itrecognizes the signing authority of server 305 and the certificate iscurrent, then an acknowledgment message 332 is returned.

Smart phone 132 may present the log acknowledgment C obtained fromserver 305, if any, to charger A (111) though message 333, which charger111 may acknowledge (not shown).

Charger 111 may present data pack D to smart phone 132 in message 334,which smart phone 132 may acknowledge (not shown). Data pack D maycomprise any of status information about charger 111, transaction dataconcerning the current and previous interactions, usage data concerningprevious interaction (there has been no usage associated with thecurrent transaction as yet), and other events (e.g., load shed andmaintenance events). An example embodiment for data pack D is shown inFIG. 8 and discussed below. To be secure, data pack D should bedigitally signed by charger A (111) using a signing certificaterecognized by server 305. In an alternative example, data pack D may beencrypted, using a private key for charger 111 for which server 305knows the public key. In either example case, server 305 can securelytrust that charger 111 originated data pack D, which has not besubjected to tampering.

At 335, vehicle 130 is plugged into charger 111 and charging begins at336. The log acknowledgment message 333 and data pack message 334 andplug-in event 335 may occur in any order after the acknowledgmentmessage 324 from charger A; however, the start of charging (336) willnot occur until a certificate is presented 331 and plug-in has occurred(336).

Typically, patron 131 will leave the proximity of vehicle 130 for asubstantial portion of the charging interval. Upon return, the closeoutphase 340 begins, comprising at least the disconnection of vehicle 130from charger 111. Optionally, patron 131 may use smart phone 132 andresume application 133 to send a close out message 342 to charger A(111), to which charger A may respond with message 343 containingreceipt E. In some embodiments, the receipt may be replaced with or be aportion of an updated data pack, similar to that in message 334, butincluding details of the patron's just-concluded charging session.

Subsequently, smart phone 132 is able to send message 351 containingdata pack D to server 305. Likewise, if available, message 352containing receipt E may be sent. In some embodiments, smart phone 132may send messages 351, 352 as soon as wireless connection to server 305is obtained, for example, if application 133 remains active. In someembodiments, these messages may be embedded in outbound emails or formatsuitable for other messaging or notification systems, such that they canbe queued before the application 133 terminates, and for sending by theoperating system when the opportunity arises.

A key element of the present invention is that the operation does notrely on the smart phone 132 of patron 131 to report receipt E to server305. If that happens, server 305 receives that information sooner. Whatthe operation does rely on is that eventually, some smart phone willupload data pack D (or a more current version of it), so that allintervening transactions and operational data will ultimately bereported, even if redundantly, and thus, provides a robust reportingmethod.

Smart phone 132 is eventually expected to use process 300, or otherexample processes described below, additional times. Thus, the latestthat application 133 might be reactivated would be for entry intopre-registration phase 310, where a subsequent parking request 311 mightbe being made. At that time, a message like 351 containing data pack D(and optionally one like message 352 containing receipt E) may be sent.If not, or if there is a persistent absence of data pack messages fromsmart phone 132, then server 305 might consider smart phone 132 to havebeen compromised and cease to transact with it, or take other measures.In any case, some other smart phone (not shown, and not controlled bypatron 131) may transact with charger 111 and server 305, and a datapack comprising similar information to that in data pack D, plus datarepresentative of the transaction and usage that would have beenreported in receipt E, may be uploaded.

FIG. 4 shows a detailed transaction diagram for unassigned parkingtransaction sequence 400, in which lines 401, 402, 403, 404 correspondto smart phone 132, charger A 111, other charger 121, and server 305,respectively. Here, pre-registration phase 410 comprises a message 411from smart phone 132 to parking management server 305 in which parkingis requested. However, in this example, the parameters of the request,or of the parking facility, do not provide for parking at a specificcharger, but instead a certificate B is provided in message 412 that isgood for any charger (at least, any charger that accepts server 305 as amanagement authority allowed to authorize parking access). Further,server 305 may provide one or more log acknowledgments, e.g., C & D, forchargers A & B, respectively.

During search phase 420, “looking for any charger” messages are sent. Inone example embodiment, Bluetooth® inquiry messages may be used, againstimulating a response from any device recognizing the inquiry. Thisdoes not occur for message 421, which no device receives, but whencharger 121 receives inquiry message 422, it acknowledges with message424, and identifies itself as charger B (using its device address).Likewise, when charger A (111) receives inquiry message 422, it respondswith acknowledgment message 425 and its own device address. Note that,for this embodiment, since the messages are not directed to any specificdevice, messages 421 and 422 could be received and acknowledged byneither, either, or both chargers 111, 121. Here, that only message 422is received, and by both chargers 111 and 121, is just an example.

In one embodiment, upon acknowledgment of “looking for charger” message422, each acknowledging charger may start to flash green indicators(e.g., 115, 125).

Upon receipt of acknowledgment 424 from charger B (121), log D may bepresented to charger B via message 427. Upon receipt of acknowledgmentmessage 425 from charger A, log C may be presented to charger A viamessage 427. Both messages 426, 427 may be acknowledged (not shown).Embodiments using alternative communication messages 428 and 438,between stations 111 and 121, are discussed below, following thediscussion of FIG. 11.

Log in phase 430 requires a short-range interaction between smart phone132 and one charger (here, charger A, 111). The interaction must beshort range so that it is unambiguous that charger 111 is the one withwhich smart phone 132 is interacting. One example short-rangecommunication that may be used is the wireless “near fieldcommunication” (NFC) standard promoted by the NFC Forum, of Wakefield,Mass. With smart phone 132 being an NFC-enabled device, a tap 431 ofsmart phone 132 to NFC tag (not shown) on charger 111 would allowemissions from smart phone 132 to power the tag enough to send anacknowledgment 432 from the tag on charger A to smart phone 132,confirming the identify (e.g., device address) of charger A as thetapped device. Alternatively, charger A may have an NFC reader, andsmart phone 132 a tag, or they may both have active NFC readers. Thepoint of the “tap” or other short-range interaction is to identify tosmart phone 132 the correct device address for the charger, or theopposite: Identify to the charger the correct device address of smartphone 132. Either way, once identities are confirmed, smart phone 132may provide certificate B to charger A in presentation message 433(which need not be over the NFC channel). Charger A acknowledgescertificate B with message 434 and may provide data pack E in message435. At 436, plug-in occurs and charging begins at 437.

As a variation on this embodiment, message 435 could be sent duringsearch phase 420, after acknowledgment 425. Likewise, a messagecontaining data pack F from charger 121 might be sent followingacknowledgment 424.

The balance of the transaction sequence (e.g., closeout and re-registerphases) is as in transaction sequence 300.

FIG. 5 shows a detailed transaction diagram for another unassignedparking transaction sequence 500, in which lines 501, 502, 503, 504correspond to smart phone 132, charger A 111, other charger 121, andserver 305, respectively. In pre-registration phase 510 and parkingrequest message 511, certificate message 512, and log acknowledgmentmessage 513 are similar to messages 411, 412, 413 in pre-registration400. However, in search phase 520, instead of using wireless to find anappropriate charger, patron 131 is allowed to pull car 130 into anyavailable parking spot 110, 120 for which the charger 111, 121 shows agreen light 115, 125 (or at least not a red light 114, 124). In otherexample embodiments, patron 131 may pull into any available parking spot110, 120. In the example shown in FIG. 5, at 521, patron 131 parksvehicle 130 in parking spot 110, corresponding to charger A (111).

At 522, patron 131 uses application 133 on smart phone 132 to scan abarcode (not shown) on charger A. For example, a two-dimensionalbarcode, such as the Quick-Response ‘QR’ codes defined in ISO/IEC18004:2006) may be used, and may contain enough information to conveythe device address (e.g., BD_ADDR) for wireless communication withcharger A (111).

Having obtained the device address, smart phone 132 can issue a “lookingfor charger A” message 523, in the manner of FIG. 3, with theacknowledgment message 524 from charger A being the response, at whichpoint smart phone 132 may present log acknowledgment C to charger A inmessage 525.

Log in phase 530 has certificate presentation message 531 delivered bysmart phone 132, which is acknowledged by message 532. Charger 111 mayprovide data pack E in message 533. And again, plug-in event 534 isfollowed by the start of charging 535.

Note in this example transaction sequence that presentation of the logacknowledgment C to charger A occurred during search phase 520, ratherthan in the log in phase 530 after certificate B was acknowledge inmessage 532, as was shown in transaction sequence 300. These examplesillustrate that some elements of these transactions are flexible andhave a tolerance for non-strict ordering.

FIG. 6 shows a flowchart for an access control and reporting process 600as performed by any of the example transaction sequences in FIGS. 3-5.At 601, the process begins when a patron 131 has a device, such as asmart phone or dashboard appliance, which is able to communicate withparking management server 305. The communication may be wireless and thecommunication channel permitting this communication may comprise theInternet. For convenient and clear discussion, a premise in thisdescription is that the device is smart phone 132.

At 602, patron 131 uses smart phone 132, for example running application133, to request electric vehicle parking and in response to the requestobtains a parking authorization certificate from server 305. The requestcan be very specific, for example, “I need to park my EV at 123 Main St.today at noon,” or much more general, “I will be parking my EV in SantaBarbara, later this week,” or something in between (e.g., parking at 123Main St., later this week). The certificate, too, may be very specific,or more general. For example, the certificate might be valid only at onespecific charging station, and only for a particular interval, e.g.,today from noon until 2 PM; or the certificate might be valid at any ofseveral specific charging stations at a particular facility, again fromnoon until 2 PM today. Or, for some 2 hour period between noon and 5 PM,for example. Such certificates would constitute a “parking reservation”.In another example, a more general certificate might be valid all week,at any charging station in the city under the management of server 305.

On some occasions, in some embodiments, at 603, while smart phone 132 isstill in communication with server 305, smart phone 132 receives one ormore log acknowledgment messages, each corresponding to a specificcharging station. A log acknowledgment message for a charging station isderived from parking management server database 620, and indicates themost current record (or date) received from that charging station. Sucha message will tell the corresponding charging station that thoserecords have been successfully received by server 305 and need no longerbe retained by the charging station, thus limiting the amount of data tobe stored locally on a charger.

At 604, smart phone 132 finds and makes connection with a charger. Ifthe parking authorization certificate is directed to a particularcharging station (e.g., 111), then smart phone 132 may use wirelesscommunication to search for that particular charging station. Whenfound, the smart phone 132 and charging station 111 may collaborate todirect patron 131 and vehicle 130 to an appropriate parking space (e.g.,110). A broader search may be made if various charging stations would beappropriate. In cases where a wireless search results in an ambiguoussituation, then additional search mechanism (e.g., NFC 431, or barcodereading 522) may be used to complete the search and identify the correctcharging station.

At 605, smart phone 132 may deliver any log acknowledgment messagesapropos to any charging station contacted in the search of 604. Acharging station receiving an appropriate log acknowledgment message maytruncate its charger log 630 in accordance with the message, providedthe message can be trusted (e.g., as might be ensured by a valid digitalsignature from a recognized authority).

Note that use of acknowledgment logs at 605 is optional, though useful.It is possible for a charging station to be provided with adequatememory and to operate under a policy to delete records that become olderthan some predetermined age. Another alternative is to only keep themost recent records, up to some predetermined number. Still anotheralternative is to keep the most recent records up to some maximum amountof memory. Yet another alternative would be to keep each record until ithas been reported (at 607, below), at least a predetermined number oftimes. Still other strategies (including a mix of those mentioned) maybe used to constrain the amount of memory and age of records representedby the log data (at 607, below).

At 606, the smart phone 132 provides to the charging station (e.g., 111)found at 604 the parking authorization certificate acquired at 602. Thecharging station may accept this certificate, provided the certificatecan be trusted (e.g., again, as ensured by a valid digital signaturefrom, or encryption by, a recognized authority). The transaction may berecorded in charger log 630 of charging station 111. In response to thepresentation of a valid certificate, the charging station is enabled andmay charge a connected vehicle.

At 607, while the smart phone 132 and charging station 111 are incommunication, the charging station may send log data from charger log630 to smart phone 132, which may further be digitally signed orencrypted by charging station 111. Note that this data is not erasedfrom the charger log 630 at this time, but is kept until a future logacknowledgment permits the erasure, as discussed above in conjunctionwith 603. Smart phone 132 keeps this log data until it is transferred toserver database 620 at 609.

At 608, vehicle 130 is connected to enabled charging station 111 andundergoes a charge while parked. Upon completion of the charge (ordisconnection from vehicle 130), charger 111 may disable and may updatecharger log 630 with information regarding electricity usage, and othertransactional (e.g., stop time) information. Other information may belogged in charger log 630, for example operational information (e.g.,load shed events or access door open/close events, etc., which may berecorded as they occur), or environmental information (e.g., internal orexternal temperatures, which may be logged periodically, or when certainthresholds are exceeded).

At 609, which may occur before, while, or after charging station 111charges vehicle 103, smart phone 609 communicates with server 305 toprovide the log data received at 607 to server database 620.

Note that 606 & 607 could occur simultaneously, or in a different order,and that log data, as at 607, might be accepted from other chargingstations, too, for example during the search at 604.

In some embodiments, as a matter of business policy, parkingauthorization certificates might be single use, or under a differentpolicy, may be used more than once. Application 133 would be programmedto obey the policy, and an analysis of logs provided by chargingstations and transferred to server database 620 through smart phone 132could determine instances where the policy has been violated.

From the charging station point of view, access control and reportingprocess 600 looks like this: At 604, a charging station is contacted bya first smart phone. This first smart phone offers a first parkingauthorization certificate at 606, which the charging station accepts tocreate a first transaction and enable charging. The first transaction islogged in charger log 630, comprising at least data representing thefirst certificate, and may further comprise start time or otherinformation. When charging 608 is complete, energy usage and/or totalconnection time may be appended to the record of the first transactionin charger log 630. At 607, a copy of log data from charger log 630,including data representing the first transaction, is provided to asecond smart phone (which could be the first smart phone having returnedat the end of the charging session, or a different one, for examplepresenting a certificate of its own) for delivery to parking managementserver 305. At 605, a log acknowledgment message may be received from athird smart phone, the message indicating that log records from thecharging station representing at least the first transaction have beenreported to the parking management server 305 and no longer need beretained, in response to which the data representing the firsttransaction in charger log 630 is deleted.

Note that what is here referred to as the third smart phone, may be thefirst smart phone: For example, after having initiated charging, thepatron with the first smart phone returns, having parked and charged forsome time. While he disconnects his vehicle from charging station 111,the first smart phone might be engaged in live, wireless connectionswith both server 305 and charging station 111 at approximately the sametime, for example while the vehicle is being disconnected from cable112, and thereby providing contemporaneous log transfer (in the role ofsecond smart phone) and acknowledgment (in the role of third smartphone); or in a different example, the first smart phone might bereturning the following day with a new certificate for presentation, butalso bearing a log acknowledgment (in the role of third smart phone) fora log delivered to the server yesterday, by the second smart phone.Further note, that over multiple interactions, log data representing thesame transaction records may be provided on more than one occasion andthus to more than one smart phone, because until a log acknowledgmentmessage is received at 605 (or other criteria is met, according topolicy, as discussed above with respect to alternative to 605), chargingstation 111 will repeatedly attempt to transmit log data to parkingmanagement server 305. The redundancies of repeated reporting arehandled at the server 305 or in database 620 (some examples of this areseen in the discussion regarding FIG. 9).

In an underground parking structure, having little or no wirelesscommunication with server 305, charging station would be found by afirst smart phone at 604, accept a certificate from it at 606, and offercharging at 608, which would be noted in a first transaction record incharger log 630. Later, after charging, 608 is complete and the firstsmart phone has departed, the charging station connects with a secondsmart phone to which is provided a log message, including the firsttransaction record at 607. That second smart phone and log message aretransported out of the underground parking structure, wherecommunication with server 305 is available, and the log is transferredto server database 620. Still later, the charging station connects withthird (different) smart phone that had received a log acknowledgmentmessage from server 305 at 603, which is provided to the chargingstation at 605, which permits the deletion of the first transactionrecord from log 630.

From the foregoing, though somewhat dependent upon implementation, itwill usually be the case that at least two of the first, second, andthird smart phones (wireless, mobile computing devices) will be distinctdevices, and often the case that all three will be distinct.

FIGS. 7A and 7B show example embodiments of the parking authorizationcertificates provided by server 305 to smart phone 132 and later bysmart phone 132 to charging station 111. Note that the example of thesefigures does not include any encapsulation, compression, or encryptionthat might be appropriate when embedding the certificate (or indiscussions below, logs and log acknowledgments) in messages.

FIG. 7A shows a secure certificate 700 suitable for use in thetransactions of FIG. 3, wherein a particular charging station “A” hasbeen assigned. Opening and closing tags 701, 702 bound the certificateitself, which is in turn secured by the signature presented in 703. Thesignature 703 may be sufficient for an embodiment where the signingcertificate and algorithm used by server 305 for the creation of securecertificate 700 is predetermined and known to the intended recipients,such as charging station 111. Alternative embodiments requiring morerobustness might use the more versatile secure document signaturesstandardized in “WL Signature Syntax and Processing,” by the World WideWeb Consortium, Cambridge, Mass., but is not used in these examples forbrevity.

The certificate comprises the elements presented between tags 701, 702.

Certificate identifier 710, in this example a UUID (universally uniqueidentifier, a standard documented in ITU-T Rec. X.667), provides thiscertificate 700 with a unique ID, which can subsequently be used toidentify this certification to the system (for example, in logs). Thisallows server 305 to track and report usage of this certificate fromlogs that may be generated and returned at a later time. Issue dateelement 711 represents the creation date of secure certificate 700 byserver 305.

For use the transaction sequence 300, secure certificate 700 comprises acharger ID element 712, which limits applicability of this certificateto a specific charging station (111) having the identity of the UUID“11111111-1111-1111-1111-111111111111”. As information for use by smartphone 132 during search phase 320 and the construction of “looking forA” messages 321, 322, 323, the charger communications identity element713 provides the device address (e.g., BD_ADDR) associated with chargingstation 111. In this example, secure certificate 700 is valid and wouldbe acceptable by charging station 111 between the dates and timesspecified in the elements reservation date 714, and reservation end date715, i.e., from 8:15 PM on February 14th until four hours later.

Upon receipt of secure certificate 700 in message 331, charging station111 can: a) compute the hash of the certificate portion from 701 to 702;b) decrypt the signature value 703 using the public key for server 305;and c) compare the results of a) and b). If they match, then thecertificate may be trusted, whereas if they do not match, thecertificate (or signature) has been accidentally damaged or deliberatelyaltered and should not be trusted.

In some embodiments, the charger ID element 712 might be one of a listof charger ID elements (not shown) for which the secure certificatewould be valid. A corresponding device address could be included foreach. In still other embodiments, the device address 713 would fulfillthe role of charger identity 712, and a separate charger identity 712would not be provided. In still other embodiments, where chargeridentity 712 is provided and device address 713 is not provided, thenthe “looking for A” transactions 322 and 323 would comprise a generalinquiry for any charger, where the recipient chargers reply with theircharger identity, which is then compared to those listed in thecertificate. A match represents an appropriate charging station beingfound.

FIG. 7B shows a different secure certificate 720, comprising thecertificate from tag 721 to 722, and a corresponding signature 723(operating as described above). As with secure certificate 700, securecertificate 720 has a unique identity 730, and an issue date 731. Butrather than designating a specific charging station or reservationinterval, secure certificate 720 comprises expiration date 732. Thus,secure certificate 720 is valid for any participating charging stationfrom the time it was issued until three days later. Secure certificate720 would be usable in transaction sequence 400, where search 420 doesnot require any specific charging station.

FIG. 8 shows an example secure log 800, comprising the log from tag 801to 802, and the digital signature 803, as might have been provided tosmart phone 123 as data pack D in message 334.

The identity of the charger providing secure log 800 is given at 811.The other data contained in this log will be associated with theindicated charging station when stored in server database 620. Uponreceipt, the server 305 can use this identity to determine appropriateparameters for checking signature 803, such as the public keycorresponding to the indicated charging station. This would also be usedin an alternative embodiment where charging station 111 encryptedportions of the log.

The date and time upon which the log was created is provided in element812. If server 305 has already accepted a log created at a later date,then this log may be superfluous and might be ignored.

The log may indicate one or more previously received log acknowledgmentswith corresponding elements 813, in which a unique identifier 814 forthe log acknowledgment is given (see discussion regarding FIGS. 10A,10B), as is the date 815 on which the acknowledgment was received bycharging station 111.

A status list starting at tag 820 and running to tag 829 may beincluded, within which each status entry, (only one shown for brevity)starting at tag 821, comprising the status date 822 and whateverenvironmental data might be desired, for example, the status 823 of aninternal back-up battery or then-current internal temperature 824. Otherstatus information citing minimums, maximums, totals, averages, orcounts might be provided (none shown), for example the total hourscharging station 111 was plugged into vehicles between the log date 812and the most recent acknowledgment received date 815, or since the priorstatus entry (e.g., in embodiments where status elements 821 are createdfor each day).

An element for listing events starts at tag 830 and runs to tag 839. Inthis example, four event elements are shown starting at tags 840, 850,860, and 870. Each has a corresponding sequence number 841, 851, 861,871, and date 842, 852, 862, 872. The sequence numbers are used byserver 305 when creating a log acknowledgment message, so that thecharging station is informed, upon receipt, that all events up to andincluding a particular one have been successfully received by parkingmanagement server 305, need not be subsequently reported again, and somay be deleted from memory.

Here, events 840, 850, and 870 are events where parking authorizationcertificates having identities 843 (corresponding to secure certificate700), 853 (corresponding to secure certificate 720), and 873 wereaccepted. Each vehicle connection lasted until the corresponding stopdate 844, 854, 874, and consumed the electrical power known to thecharging station and reported at 845, 855, 875. From this information,server 305 can determine which certificates were used, when, theduration of parking (assuming the vehicle remained plugged in throughoutits stay in the parking place 110), and the energy consumed; which whenjoined with the information already associated with the certificates, issufficient to properly debit or bill the associated accounts and/orotherwise track and report on usage.

Event element 860 is an exception to the above, where for thirty minutesfrom 862 to 864, charging station 111 was directed to shed load 863,during which interval, no vehicle charging would have occurred. Sincethis thirty-minute interval is entirely within the span of event 850,depending upon business policy, there may or may not be an adjustment tothat transaction. In some embodiments, the load-shed event might berepresented in the log within concurrent event 850, and split as neededwhere the load-shed event is only partially concurrent with other events(neither case shown).

As a matter of business policy, how a charging station should behave ifthe number of log entries (status and events) would exceed availablememory may include priorities, for example, that might first deletecertain data from status entries (e.g., battery status 823), or wholestatus entries (e.g., 821), to deleting certain events (e.g., load shedevents 860), events older than a predetermined age (e.g., three months),event details (e.g., power usage 845), and so on. Though considering thelow cost of memory and the availability of compression and encodingtechnologies, such log pruning behavior is unlikely to be used. Inextreme cases, a critical log size in a charging station might beobserved or anticipated by server 305, and a maintenance operatordispatched specifically to collect the current log and subsequentlyprovide a log acknowledgment.

One example schema 900 suitable for implementing server database 620 isshown in FIG. 9. Schema 900 comprises owners table 910, which listsentities that own participating charging stations; chargers table 920,which lists the charging stations served by parking management server305; accounts table 930, which lists all the patrons participating inthe system; certificates table 940, which tracks all the parkingauthorization certificates issued; events table 950, which are thoseevents returned in logs; logs table 960, which represents the logsreturned, less the events they contained; log-events linking table 970,which associates each event record in events table 950 with the one ormore log records in log table 960; acks table 980, which lists each logacknowledgment created; and logs-acks linking table 990, whichassociates acknowledgment records in acks table 980 with each log recordin table 960 that reported having received the log acknowledgment.

In other schema embodiments, different organizations of the data may beselected, for example, to break out status entries from the records inlogs table 960 as are event records in table 950, if such was needed tobetter analyze and report on daily or hourly status data (none shown)that was being collected.

In owners table 910, each record provides business information such asthe owner's name, contact information, and payment information. Thisallows the parking management system comprising server 305 to computeand transfer payments as appropriate to the owners, for parking andcharging that takes place involving their chargers. It also providesinformation necessary to contact the owners if other issues arise (e.g.,maintenance needed) with their charging station.

Each record in chargers table 920 contains a unique identifier for thecharging station (e.g., as may be used in the charger identificationelement 712 in certificate 700, and elsewhere). The location of thecharger is also recorded, for example to provide map coordinates to apatron looking for a charging station (which might also have beenincluded in secure certificate 700), as is the communication identifier(e.g., device address/BD_ADDR), included in the certificate as element713. Each charger has exactly one owner, as shown with ‘owns’relationship 921, though each owner may own multiple charging stations.

Accounts table 930 has for each record a unique account identifier,username, contact information, and billing information (which maydescribe a prepaid account, which subscription plan the patron hasselected, credit card billing preferences, etc., according to businessneeds and policies).

Certificates table 940 generates a record for each parking authorizationcertificate made, which includes the unique certificate identifier(e.g., 712). The account ID for which the certificate is made is alsorecorded, thereby creating ‘for account’ relationship 943, since eachcertificate is made on the request from a patron. The other informationrecorded is also found in the various kinds of certificates: issue date(711, 731), expires date (732), reservation date (714), reservation enddate (715), and charger ID (712). Note that not all fields are used inevery kind of certificate, in which case the field in the record may beset to null. When present, the charger ID field forms ‘for chargingstation’ relationship 942.

Embodiments of the present invention should comply with Article 625 ofthe National Electrical Code, and if used to support an electric vehiclefeeding energy back into the electric grid, then embodiments shouldfurther comply with Article 705.

Events reported in logs are parsed into records in events table 950.Each event record may be given a unique event ID for use in the database(as shown), or the fields corresponding to the log's charger ID (811)and event's sequence number (e.g., 841) may be used together as acomposite key for the table (though not used here). The “event kind”field would differentiate between parking events and load shed events,as shown in log 800. Other kinds of events may include power failure,maintenance, access (e.g., door open/door closed), etc. In somealternative embodiments, the status elements in list element 820 mightbe logged, provided, and recorded as events having their owncorresponding event kinds instead of being treated separately. Thecharger ID field creates charger-event relationship 952, so that thehistory of activities for a charger is easily accessible. For thoseevents involving a certificate (e.g., event 840 involves certificate843), the population of the certificate ID field creates ‘used’relationship 954, which may represent a billable event.

As shown, log records in table 960 are provided with a unique identifierfor use in database 620, though in other embodiments, a composite keymade up of the charger ID (from 811) and log date (from 812) could beused (though not here). The charger ID field provides ‘log from’relationship 962, and the records in linking table 970 provide themany-to-many relationship comprising 975, 976 that records in which logswhich events were reported (since an individual event might be reportedmultiple times). Log records in table 960 might include an additionalfield for account ID (not shown) to maintain a record of which patronshad carried which logs.

Log acknowledgments that are generated are recorded as records in 980,each having a unique ID as used in 814, 1010, and 1030, though inembodiments in which a single log acknowledgment message (e.g., 1020)having a single acknowledgment ID 1030 may reference multiple chargingstations (1041, 1051, 1061), the full key for table 980 would be thecompound key formed of the acknowledgment ID and charger ID fields.Charger ID also forms the ‘log ack for’ relationship 982. If eachacknowledgment message is specifically generated when a certificate isbeing requested, then a relationship 983 may be maintained by recordingthe account ID field to allow statistics to be tracked for how well logacknowledgments are being transported into what areas and by whom, whichmay allow optimizations when later log acknowledgments are beingprovided by server 305.

Log acknowledgments received is a many-to-many relationship maintainedby the records in table 990 each associating a log acknowledgment record(via 998, which may use the compound key discussed above) with a log(via 996) indicating not only that the log acknowledgment was received,but recording when (815), in the acknowledgment date field. Theserecords are also useful for statistical analysis, when gauging how bestto provide charging stations with log acknowledgments, and how long thatis likely to take.

FIG. 10A show one example form for secure log acknowledgment 1000, whileFIG. 10B shows another secure log acknowledgment 1020. Each provides thelog acknowledgment from tags 1001, 1021 to 1002, 1022 and a securesignature 1003, 1023, all respectively. Each also has a uniqueacknowledgment ID 1010, 1030 and issue date 1011, 1031. However, thefirst, in FIG. 10A, contains a log acknowledgment for only one charger1012, and indicates the last sequence number 1013 received as of theissue date 1011. In contrast, the second log acknowledgment, in FIG.10B, contains a list from 1032 to 1033 of individual acknowledgments1040, 1050, 1060, each calling out a different charger 1041, 1051, 1061with corresponding last-received log sequence numbers 1042, 1052, 1062,all respectively. The former would only be delivered to the particularcharging station identified at 1010, as done in message 333. The lattercould be used for delivery to ANY of the charging stations listedtherein, thus the single secure log acknowledgment 1020 might be used ineach of messages 426, 427 (assuming that the ID for charger B is one of1051, 1061). It would also be the case that two log acknowledgments ofthe type shown in 1000, one for each of charging stations A and B, couldbe used for messages 426 and 427, respectively.

One example configuration for charging station 111 is shown in FIG. 11,where processor 1101 controls indicators 1103 (e.g., comprising lights114, 115, but which may comprise a display screen, not shown), andcharging element 1102, which may be connected to an electric vehiclewith charging cable 112. Processor 1101 has access to storage 1104,which contains the software instructions for execution by the processor,and which provides storage for data, including event and status data tobe retained until successfully transferred (e.g., via smart phone 132)to server 305 through logs (e.g. 800) and subsequently acknowledged(e.g., by log acknowledgment 1000). Processor 1101 can communicate withexternal devices, for example smart phone 132, by long-rangecommunications module 1105 (where ‘long-range’ may be several meters tosubstantial portions of a mile, e.g., Bluetooth®, Wi-Fi).

In some embodiments, short-range communication module 1106 may beprovided, where ‘short-range’ is a distance sufficiently small for it tonot be ambiguous which charging station is conducting the transaction.Examples of short-range communication may be NFC, IrDA (as standardizedby the Infrared Data Association). So choices, e.g., NFC, would notnecessarily require connection to processor 1101, for example if an NFCtag is merely providing the device address for this charging station'slong-range communication module (as discussed above).

In other embodiments requiring ambiguity (caused by overlappinglong-range communication ranges of multiple charging stations) to beresolved, a barcode or QR code (not shown) may be presented on or nearcharging station 111 that identifies the correct device address,passcode, etc. that would disambiguate the long-range communications.

In other embodiments, the NFC tag may be located in the connector ofcharging cable 112 and read by an NFC reader located near the chargingport of the vehicle. In an alternative embodiment, a similaridentification to disambiguate the long-range communication may beprovided by wired communication through cable 112.

In still other embodiments, especially those making use of a dashboardappliance in vehicle 130 (which may be built-in), to participate in thetransactions described in place of smart phone 132, communication withcharging station 111 may be wholly or partially through charging cable112. In such embodiments, long-range communication module 1105 andantenna 113 may be unnecessary, unless communication is desired otherthan when vehicle 103 is plugged into charger 111.

Charging station 111 maintains an internal clock 1107 for use inevaluating validity of certificates by checking for valid reservationintervals (e.g., 714-715) or expiration dates (e.g., 732), and for timestamping status and event entries recorded in storage 1104 and latercompiled into secure logs (e.g. 800). If a charging station has accessto global positioning satellite signals, even only occasionally, thenGPS device 1108 can be used to accurately set clock 1107. In othercircumstances, processor 1101 may transact with one or more externaldevices (e.g., smart phone 132, or dashboard appliance) to determinemaintain the current time on clock 1107, though generally, more than oneinteraction with different devices would be used to ensure a moreaccurate time setting.

In some embodiments, charging stations may have a communication module(whether 1105 or another long-range communication module not shown) topermit charging stations sufficiently near each other to exchangeinformation. For example, stations 111 and 121 might exchange loginformation, such that each can deliver not only their own log, but alsothe log(s) of their neighbors (e.g., in data pack D at 334).Communication between proximal charging stations might be wired, or maybe wireless, for example using BlueTooth®, or Wi-Fi, ZigBee® (a wirelesstechnology standardized and promoted by the ZigBee Alliance of SanRamon, Calif.), the latter two having a nominal range of up to 100 m.Such inter-station communication is also useful with multi-station logacknowledgment 1020, as a single receiving station could re-distributethe document to other stations. For example, in FIG. 4, themulti-station log acknowledgment message received at 413 is provided tostation 111 at 426 from smart phone 132, and could be forwarded tostation 121 as message 428, which could occur in lieu of transfer 427,or in addition to it. Station 121 might then forward the message toother nearby stations (not shown). In such a case, the system stillrelies on smart phone 132 to transfer the log acknowledgment message tothe charging stations (e.g., 121), even if the delivery flows indirectlythrough another charging station (111).

A similar efficiency with respect to log messages may be obtained whereintercommunicating charging stations exchange log messages (e.g., 438)with each other. Thus, when data pack E from charger A is provided asmessage 435, it might include not only the current log from charger A(111), but also a log from station B (121), previously transferred viamessage 438. The log from station B may be aged; depending on how oftenexchanges such as 438 take place).

In some embodiments of application 133, access to data provided fromdiagnostic systems of vehicle 130 may be provided (not shown). Anexample mechanism for this is to use the on-board diagnostic port (OBDport) with a BlueTooth™ adapter such as those using the ELM 327 chipdesigned and marketed by Elm Electronics of London, Ontario, Canada. TheOBD port is standardized by the Society of Automotive Engineers in SAEJ1978 February 1998 and ISO/DIS 15031-4 and their associated documents.This provides a standard way to access certain vehicle-relatedinformation, such as the VIN (vehicle identification number) and in somevehicles, the odometer. In such an embodiment, when a parking request(e.g., 311, 411, 511) is further made in the context of a managedvehicle fleet, then application 133 on smart phone 132 may obtainvehicle data accessed from the OBD, e.g., the VIN and/or odometer. Suchinformation may be presented with the certificate request and tracked byserver database 620, and may be included with the presentation of thecertificate B (e.g., 331, 433, 531) to the charging station for laterincorporation into logs, for example by inclusion in the correspondingevents (such as 840, though no fleet information or VIN/odometer data isshown). Such mechanisms may help to minimize fraud, since the VIN couldbe registered in parking management database 620 as being associatedwith a fleet (not shown), and the odometer readings need to behavereasonably between transactions, that is, progressing monotonically, andrising in approximate proportion to energy expended, including fuelconsumed.

The application 133 may further include an option to accept feedbackfrom patron 130 with respect to the current condition of one or morecharging stations, with such feedback being sent to server 305. Anexample use of such a capability would be to allow a patron to alert thecharging station management that there is a safety hazard (e.g., frayedcable, damaged connector, poor lighting), or other complaint regarding aparticular charging station.

For any additional data services (e.g., OBD data, customer complaints)communication with the charging station may provide one other service,that of authentication. For example, if at 331 a certificate ispresented to station 111 along with OBD information, the acknowledgment332 or receipt 343 could include the same OBD information, but with asecure signature (not shown). Thus, application 133 would obtain anauthenticated record linking the then-current OBD data to use of thecertificate on station 111. Such information would be included whenlater in communication with server 305 (e.g., message 352).

In some embodiments, the provision (e.g., 313) and presentation (e.g.,333) of a log acknowledgment may be further accompanied by data (notshown) for the charging station comprising a software upgrade or anupdate to a database. Once provided, the authenticity of theupgrade/update would be validated, and installation would proceedaccording to policy. Such updates could also be spread to other nearbycharging stations if they are independently in communication with eachother. If software updates are particularly large, they might bedistributed in smaller chunks, such that the update would be received inindividual pieces, but would not be installed until all pieces had beendelivered. This would be used to prevent excessive transfer times whensmart phone 132 is transferring the update to the charging station.Status entries in log 800 might be added to indicate which portions of aparticular update had been received or which updates had been installed(none shown), which would allow server 305 to better manage suchdistributions.

In messages containing the logs, certificates, log acknowledgments,auxiliary data (e.g., ODB information), software updates, etc., thecontents may be encrypted, as previously discussed. Further, thecontents may be padded to obscure nature of the contents. In this way,transfer of a certificate with or without a software update, or a logacknowledgment for one (1000) or many (1020) chargers, might beexternally indistinguishable. This could be further extended to includedummy logs or dummy log acknowledgments, so that each request 311 isalways provided with a log acknowledgment 313 (whether or not a dummy),and obtains from charging station 111 a data pack 344 (whether or not adummy), for use in measuring the statistical efficacy of smart phone132, application 133, and patron 130 in transferring messages.

Various additional modifications of the described embodiments of theinvention specifically illustrated and described herein will be apparentto those skilled in the art, particularly in light of the teachings ofthis invention. It is intended that the invention cover allmodifications and embodiments, which fall within the spirit and scope ofthe invention. Thus, while preferred embodiments of the presentinvention have been disclosed, it will be appreciated that it is notlimited thereto but may be otherwise embodied within the scope of thefollowing claims.

What is claimed is:
 1. A method for the control of dispensing, as offuel or electrical energy, to vehicles, the method comprising: a)accepting a first data, with a first station comprising a memory, from afirst mobile computing device of a first patron, the first datarepresentative of at least a certificate, the certificate created by amanagement system and representing an authorization for dispensing; b)dispensing to a vehicle, with the first station, in response to thefirst data; c) making a record in the first station, the recordcomprising a second data representing the dispensing and at least anidentifying portion of the certificate; d) providing a third data, bythe first station, to a second mobile computing device of any patron,the third data deliverable by the second mobile computing device to themanagement system, the third data representative of the record.
 2. Themethod of claim 1, further comprising: e) accepting a fourth data, withthe first station, from a third mobile computing device of any patron,the fourth data representative of at least an acknowledgment of therecord, the acknowledgment created by the management system andrepresenting receipt by the management system of the third data; and, f)deleting the record from the first station in response to the fourthdata.
 3. The method of claim 2, wherein the fourth data comprises adigital signature by the management system and e) accepting the fourthdata further comprises validating the signature.
 4. The method of claim2, wherein the fourth data comprises an encrypted portion by themanagement system and e) accepting the fourth data further comprisesdecrypting the encrypted portion.
 5. The method of claim 1, wherein atleast one of the first and second mobile computing devices is a smartphone.
 6. The method of claim 1, wherein at least one of the first andsecond mobile computing devices is a dashboard appliance in the vehicle.7. The method of claim 1, wherein a portion of the second datarepresenting the dispensing is representative of at least one of acurrent date, a duration of the dispensing, and a quantity dispensed. 8.The method of claim 1, wherein the first data is further representativeof a device address of the first station, the method further comprising:e) responding to a wireless search for the device address by the firstmobile computing device, with a visible indicator associated with thefirst station.
 9. The method of claim 1, further comprising: e)responding to a wireless search for any station by the first mobilecomputing device, with a visible indicator associated with and signalingthe availability of the first station.
 10. The method of claim 1,wherein the third data is further representative of a status of thefirst station.
 11. The method of claim 1, wherein the first datacomprises a digital signature by the management system and a) acceptingthe first data further comprises validating the signature.
 12. Themethod of claim 1, wherein the first data comprises an encrypted portionby the management system and a) accepting the first data furthercomprises decrypting the encrypted portion.
 13. The method of claim 1,wherein d) providing the third data is further through a second stationand the first station has communication with the second station.
 14. Afirst station, for dispensing fuel or electricity to vehicles,comprising: a processor; a communication module connected to theprocessor to provide communication with mobile computing devices; adispensing element, controllably enabled by the processor, fordispensing at least one of fuel and electricity; and, a memoryaccessible to the processor, the memory containing executableinstructions, which when executed by the processor perform a process of:a) accepting a first data, through the communication module, from afirst mobile computing device of a first patron, the first datarepresentative of at least a certificate, the certificate created by amanagement system and representing an authorization for dispensing; b)dispensing to a vehicle, with the dispensing element, in response to thefirst data; c) making a record in the first station, the recordcomprising a second data representing the dispensing and at least aportion of the certificate; d) providing a third data, through thecommunication module, to a second mobile computing device of any patron,the third data deliverable by the second mobile computing device to themanagement system, the third data representative of the record.
 15. Thestation of claim 14, wherein the process further comprises: e) acceptinga fourth data, through the communication module, from a third mobilecomputing device of any patron, the fourth data representative of atleast an acknowledgment of the record, the acknowledgment created by themanagement system and representing receipt by the management system ofthe third data; and, f) deleting the record from the first station, inresponse to the fourth data.
 16. The station of claim 15, wherein thefourth data comprises a digital signature by the management system ande) accepting the fourth data further comprises validating the signature.17. The station of claim 15, wherein the fourth data comprises anencrypted portion by the management system and e) accepting the fourthdata further comprises decrypting the encrypted portion.
 18. The stationof claim 14, wherein the communication module comprises a datatransceiver in an ISM radio band.
 19. The station of claim 14, whereinthe communication module comprises a data transceiver in a 2.4 GHz radioband.
 20. The station of claim 14, wherein a portion of the second datarepresenting the dispensing is representative of at least one of acurrent date, a duration of the dispensing, and a quantity dispensed.21. The station of claim 14 further comprising: a visible indicator;and, wherein the first data is further representative of a deviceaddress of the communication module; and, the process further comprises:e) responding to a wireless search for the device address by the firstmobile computing device, with the indicator.
 22. The station of claim14, further comprising: a visible indicator; and, wherein the processfurther comprises: e) responding to a wireless search for any station bythe first mobile computing device, by signaling availability with theindicator.
 23. The station of claim 14, wherein the third data isfurther representative of a status of the first station.
 24. The stationof claim 14, wherein the first data comprises a digital signature by themanagement system and a) accepting the first data further comprisesvalidating the signature.
 25. The station of claim 14, wherein the firstdata comprises an encrypted portion by the management system and a)accepting the first data further comprises decrypting the encryptedportion.
 26. The station of claim 14, wherein d) providing the thirddata is further through a second station and the communication modulehas communication with the second station.